PO-2816 : generate v2 user state from database#473
Merged
stephenmagill merged 6 commits intomasterfrom Apr 15, 2026
Merged
Conversation
Sean-Reed-CGI
commented
Apr 2, 2026
11c3c4a to
0882584
Compare
Sean-Reed-CGI
commented
Apr 7, 2026
Sean-Reed-CGI
commented
Apr 7, 2026
Ben-Edwards-cgi
approved these changes
Apr 8, 2026
fe09046 to
271232e
Compare
271232e to
33d2054
Compare
Fixed build after conflicts
Chi-cgi
approved these changes
Apr 14, 2026
updated code and tests for AC3. updating last login when newlogin header is present and true.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PO-2816
BE - Update user state to use Role based access control (RBAC), domains and cache (Opal Mode)
We are adding a new endpoint which returns an updated (V2) UserState DTO which has the shape required for the Tactical User Management Solution.
JPA Modelling Note
We have the following hierarchy of JPA entities:
UserEntity-> BusinessUnitUserEntity->BusinessUnitUserRoleEntity
This is modelled with 2 layers of @onetomany which are left as lazily loaded, as I think we don’t want permissions loaded in every use case.